Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix/subprocess handling with QRM #61

Merged
merged 20 commits into from
Aug 25, 2023
Merged

Fix/subprocess handling with QRM #61

merged 20 commits into from
Aug 25, 2023

Conversation

LaviniaStiliadou
Copy link
Contributor

Short Description

As described in the issue, when a replacement of a QRM contains subprocesses, all subprocesses are expanded independent of the form within the replacement.

Proposed Changes

  • extract isExpanded attribute from replacement of a QRM
  • delete additional bpmn:BPMNDiagram elements
  • delete isExpanded attribute from shape after it is available in the diagram element

@LaviniaStiliadou LaviniaStiliadou linked an issue Jun 4, 2023 that may be closed by this pull request
Copy link
Collaborator

@wederbn wederbn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fails for me with the following error message when transforming this workflow:

image

I think this workflow would be a nice test case, as it combines multiple features of the modeler.
Then, one of the asserts could validate that isExpanded is set correctly

@wederbn wederbn merged commit 64100ce into master Aug 25, 2023
1 check passed
@wederbn wederbn deleted the fix/subprocess-handling branch August 25, 2023 10:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Subprocess handling within QRMs
3 participants